User equipment, base station apparatus, communication method of a user equipment and communication method of a base station apparatus

ABSTRACT

Method and apparatus use a value tag in conjunction with transmission and/or processing of system information in a wireless communication network, especially in conjunction with second type system information or non-essentially type system information.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.15/659,027 filed Jul. 25, 2017, which claims the priority and benefit ofU.S. Provisional Patent application 62/367,590, filed Jul. 27, 2016,both of which are incorporated herein by reference in their entirety.

FIELD

The technology relates to wireless communications, and particularly tomethods and apparatus for requesting, transmitting, and using systeminformation (SI) in wireless communications.

BACKGROUND

In wireless communication systems, a radio access network generallycomprises one or more access nodes (such as a base station) thatcommunicate on radio channels over a radio or air interface with pluralwireless terminals. In some technologies, such a wireless terminal isalso called a User Equipment (UE). A group known as the 3rd GenerationPartnership Project (“3GPP”) has undertaken to define globallyapplicable technical specifications and technical reports for presentand future generation wireless communication systems. The 3GPP Long TermEvolution (“LTE”) and 3GPP LTE Advanced (LTE-A) are projects to improvean earlier Universal Mobile Telecommunications System (“UMTS”) mobilephone or device standard in a manner to cope with future requirements.

In typical cellular mobile communication systems, the base stationbroadcasts on the radio channels certain information which is requiredfor mobile stations to access the network. In Long-Term Evolution (LTE)and LTE Advanced (LTE-A), such information is called “systeminformation” (“SI”). Each access node, such as an evolved NodeB (“eNB”),broadcasts such system information to its coverage area via severalSystem Information Blocks (SIBs) on downlink radio resources allocatedto the access node.

A wireless terminal (“UE”), after entering a coverage area of an eNB, isrequired to obtain all the SIBs which are necessary to access thesystem. For sake of UEs under coverage, the eNB periodically broadcastsall SIBs relevant for offered services, not just SIBs that are requiredfor access to the system. Each type of SIBs is transmitted in adesignated radio resource(s) with its own pre-determined/configurablefrequency.

This all-broadcast-based periodic delivery method (e.g., collectivebroadcast of all SIBs, not just those necessary for system access) isefficient under a condition where many UEs are almost always flowinginto the coverage area (such as a macro cell). However, this approachmay result in wasting valuable radio resources in case of small celldeployment. Therefore, more efficient methods of SIB transmission aredesired.

What is needed, therefore, and an example object of the technologydisclosed herein, are methods, apparatus, and techniques for moreefficient transmission of system information blocks (SIBs).

SUMMARY

In one of its example aspects, the technology disclosed herein concernsan access node of a radio access network. The access node comprisesprocessor circuitry and a transmitter. The processor circuitry isconfigured to generate a value tag associated with system information.The system information facilitates the use of communication servicesprovided by the access node. The transmitter is configured to transmit,over a radio interface, node-available system information comprising anidentification of the system information and the value tag associatedwith the system information.

In another of its example aspects, the technology disclosed hereinconcerns a method in an access node of a radio access network. In abasic implementation the method comprises generating a value tagassociated with system information, the system information facilitatingthe use of communication services provided by the access node; and,transmitting over a radio interface node-available system informationcomprising an identification of the system information and the value tagassociated with the system information.

In another of its aspects, the technology disclosed herein concerns awireless terminal which communicates over a radio interface with anaccess node of a radio access network. The wireless terminal basicallycomprises a receiver and processor circuitry. The receiver is configuredto receive from the access node a system information availabilitymessage comprising an identification of node-available systeminformation and a node-transmitted value tag associated with thenode-available system information. The processor circuitry is configuredon the basis of the node-transmitted value tag to determine whether torequest that the node-available system information be transmitted to thewireless terminal.

In another of its example aspects, the technology disclosed hereinconcerns a method in a wireless terminal that communicates over a radiointerface with an access node of a radio access network. In a basic modethe method comprises receiving from the access node a system informationavailability message comprising an identification of node-availablesystem information and a node-transmitted value tag associated with thenode-available system information; and, on the basis of thenode-transmitted value tag determining whether to request that thenode-available system information be transmitted to the wirelessterminal.

BRIEF DESCRIPTION OF THE DRAWINGS

The foregoing and other objects, features, and advantages of thetechnology disclosed herein will be apparent from the following moreparticular description of preferred embodiments as illustrated in theaccompanying drawings in which reference characters refer to the sameparts throughout the various views. The drawings are not necessarily toscale, emphasis instead being placed upon illustrating the principles ofthe technology disclosed herein.

FIG. 1 is a schematic view showing an example communications systemcomprising a radio access node and a wireless terminal, and wherein theradio access node provides a value tag for system information (SI).

FIG. 2 is a diagrammatic view of a node-available system informationmessage according to an example embodiment and mode.

FIG. 3 is a flowchart showing an example, representative, basic acts, orsteps performed by the radio access node of FIG. 1.

FIG. 4 is a flowchart showing an example, representative, basic acts, orsteps performed by the wireless terminal of FIG. 1

FIG. 5 is a schematic view showing an example communications systemcomprising a radio access node and a wireless terminal, and wherein theradio access node provides a value tag for system information (SI) alongwith differentiated delivery of system information (SI).

FIG. 6 is a diagrammatic view showing an example message flow for theexample communications system of FIG. 5.

FIG. 7 is a diagrammatic view showing an example format of an EssentialSystem Information message according to an example implementation of thesystem of FIG. 5.

FIG. 8 is a schematic view showing an example communications systemcomprising a radio access node and a wireless terminal, and wherein theradio access node provides a value tag for system information (SI) alongwith a definition of a base of second type system information to whichthe value tag applies.

FIG. 9 is a diagrammatic view showing an example message flow for theexample communications system of FIG. 8.

FIG. 10 is a schematic view showing an example communications systemcomprising a radio access node and a wireless terminal, and wherein thewireless terminal provides a stored value tag for stored second typesystem information (SI) when requesting second type system informationfrom the radio access node.

FIG. 11 is a diagrammatic view showing an example message flow for theexample communications system of FIG. 10.

FIG. 12 is a flowchart showing an example, representative, basic acts,or steps performed by the radio access node of FIG. 10 in implementingcertain acts of FIG. 11.

FIG. 13 is a flowchart showing an example, representative, basic acts,or steps performed by the wireless terminal of FIG. 10 in implementingcertain acts of FIG. 11.

FIG. 14 is a schematic view showing an example communications systemcomprising a radio access node and a wireless terminal, and wherein theradio access node provides a value tag which is associated with a groupof plural system information blocks (SIBs).

FIG. 15 is a diagrammatic view showing an example format of an EssentialSystem Information message according to an example implementation of thesystem of FIG. 14, wherein multiple sibIds associated with one valueTagform a non-essential SIB group.

FIG. 16 is a diagrammatic view showing an example message flow for theexample communications system of FIG. 14.

FIG. 17 is a flowchart showing an example, representative, basic acts orsteps performed by the radio access node of FIG. 14 in implementingcertain acts of FIG. 16.

FIG. 18 is a flowchart showing an example, representative, basic acts orsteps performed by the wireless terminal of FIG. 14 in implementingcertain acts of FIG. 16.

FIG. 19 is a diagrammatic view showing an example message flow foranother example embodiment and mode that combines features of theembodiment and mode of FIG. 10 and the embodiment and mode of FIG. 14.

FIG. 20-FIG. 24 are diagrammatic views showing an example message flowsfor yet other example embodiments and modes.

FIG. 25 is a diagrammatic view showing example electronic machinery thatmay comprise node electronic machinery or terminal electronic machinery.

DETAILED DESCRIPTION

In the following description, for purposes of explanation and notlimitation, specific details are set forth such as particulararchitectures, interfaces, techniques, etc. in order to provide athorough understanding of the technology disclosed herein. However, itwill be apparent to those skilled in the art that the technologydisclosed herein may be practiced in other embodiments that depart fromthese specific details. That is, those skilled in the art will be ableto devise various arrangements which, although not explicitly describedor shown herein, embody the principles of the technology disclosedherein and are included within its spirit and scope. In some instances,detailed descriptions of well-known devices, circuits, and methods areomitted so as not to obscure the description of the technology disclosedherein with unnecessary detail. All statements herein recitingprinciples, aspects, and embodiments of the technology disclosed herein,as well as specific examples thereof, are intended to encompass bothstructural and functional equivalents thereof. Additionally, it isintended that such equivalents include both currently known equivalentsas well as equivalents developed in the future, i.e., any elementsdeveloped that perform the same function, regardless of structure.

Thus, for example, it will be appreciated by those skilled in the artthat block diagrams herein can represent conceptual views ofillustrative circuitry or other functional units embodying theprinciples of the technology. Similarly, it will be appreciated that anyflow charts, state transition diagrams, pseudocode, and the likerepresent various processes which may be substantially represented incomputer readable medium and so executed by a computer or processor,whether or not such computer or processor is explicitly shown.

As used herein, the term “core network” can refer to a device, group ofdevices, or sub-system in a telecommunication network that providesservices to users of the telecommunications network. Examples ofservices provided by a core network include aggregation, authentication,call switching, service invocation, gateways to other networks, etc.

As used herein, the term “wireless terminal” can refer to any electronicdevice used to communicate voice and/or data via a telecommunicationssystem, such as (but not limited to) a cellular network. Otherterminology used to refer to wireless terminals and non-limitingexamples of such devices can include user equipment terminal, UE, mobilestation, mobile device, access terminal, subscriber station, mobileterminal, remote station, user terminal, terminal, subscriber unit,cellular phones, smart phones, personal digital assistants (“PDAs”),laptop computers, netbooks, e-readers, wireless modems, etc.

As used herein, the term “access node,” “node,” or “base station” canrefer to any device or group of devices that facilitates wirelesscommunication or otherwise provides an interface between a wirelessterminal and a telecommunications system. A non-limiting example of abase station can include, in the 3GPP specification, a Node B (“NB”), anenhanced Node B (“eNB”), a gNB (for the 5G “New Radio” [NR]), a home eNB(“HeNB”) or some other similar terminology. Another non-limiting exampleof a base station is an access point. An access point may be anelectronic device that provides access for the wireless terminal to adata network, such as (but not limited to) a Local Area Network (“LAN”),Wide Area Network (“WAN”), the Internet, etc. Although some examples ofthe systems and methods disclosed herein may be described in relation togiven standards (e.g., 3GPP Releases 8, 9, 10, 11, and/or 12), the scopeof the present disclosure should not be limited in this regard. At leastsome aspects of the systems and methods disclosed herein may be utilizedin other types of wireless communication systems.

As used herein, the term “telecommunication system” or “communicationssystem” can refer to any network of devices used to transmitinformation. A non-limiting example of a telecommunication system is acellular network or other wireless communication systems.

As used herein, the term “cellular network” can refer to a networkdistributed over cells, each cell served by at least one fixed-locationtransceiver, such as a base station. A “cell” may be any communicationchannel that is specified by standardization or regulatory bodies to beused for International Mobile Telecommunications-Advanced(“IMTAdvanced”). All or a subset of the cell may be adopted by 3GPP aslicensed bands (e.g., frequency band) to be used for communicationbetween a base station, such as a Node B, and a UE terminal. A cellularnetwork using licensed frequency bands can include configured cells.Configured cells can include cells of which a UE terminal is aware andin which it is allowed by a base station to transmit or receiveinformation.

FIG. 1 shows an example communications system 20 wherein radio accessnode 22 communicates over air or radio interface 24 (e.g., Uu interface)with wireless terminal 26. As mentioned above, the radio access node 22may be any suitable node for communicating with the wireless terminal26, such as a base station node, or eNodeB (“eNB”), or gNB, for example.The radio access node 22 comprises node processor circuitry (“nodeprocessor 30”) and node transceiver circuitry 32. The node transceivercircuitry 32 typically comprises node transmitter circuitry 34 and nodereceiver circuitry 36, which are also called node transmitter and nodereceiver, respectively.

The wireless terminal 26 comprises terminal processor 40 and terminaltransceiver circuitry 42. The terminal transceiver circuitry 42typically comprises terminal transmitter circuitry 44 and terminalreceiver circuitry 46, which are also called terminal transmitter 44 andterminal receiver 46, respectively. The wireless terminal 26 alsotypically comprises user interface 48. The terminal user interface 48may serve for both user input and output operations, and may comprise(for example) a screen such as a touch screen that can both displayinformation to the user and receive information entered by the user. Theuser interface 48 may also include other types of devices, such as aspeaker, a microphone, or a haptic feedback device.

For both the radio access node 22 and the wireless terminal 26, therespective transceiver circuitries 32 and 42 include antenna(s). Therespective transmitter circuits 34 and 44 may comprise, e.g.,amplifier(s), modulation circuitry, and other conventional transmissionequipment. The respective receiver circuits 36 and 46 may comprise,e.g., amplifiers, demodulation circuitry, and other conventionalreceiver equipment.

In general operation node, the radio access node 22 and wirelessterminal 26 communicate with each other across radio interface 24 usingpredefined configurations of information. By way of non-limitingexample, the radio access node 22 and wireless terminal 26 maycommunicate over the radio interface 24 using “frames” of informationthat may be configured to include various channels. In LTE, for example,a frame, which may have both downlink portion(s) and uplink portion(s),may comprise plural subframes, with each LTE subframe in turn beingdivided into two slots. The frame may be conceptualized as a resourcegrid (a two dimensional grid) comprised of resource elements (RE). Eachcolumn of the two dimensional grid represents a symbol (e.g., an OFDMsymbol on the downlink (DL) from the radio access node to the wirelessterminal; an SC-FDMA symbol in an uplink (UL) frame from the wirelessterminal to the radio access node). Each row of the grid represents asubcarrier. The frame and subframe structure serves only as an exampleof a technique of formatting of information that is to be transmittedover a radio or air interface. It should be understood that “frame” and“subframe” may be utilized interchangeably or may include or be realizedby other units of information formatting, and as such may bear otherterminology (such as blocks).

To cater to the transmission of information between the radio accessnode 22 and the wireless terminal 26 over the radio interface 24, thenode processor 30 and terminal processor 40 of FIG. 1 are shown ascomprising respective information handlers. For an exampleimplementation in which the information is communicated via frames, theinformation handler for the radio access node 22 is shown as nodeframe/signal scheduler/handler 50, while the information handler forwireless terminal 26 is shown as terminal frame/signal scheduler/handler52.

The node processor 30 of a radio access node 22 also includes a systeminformation (SI) generator 54. The wireless terminal 26 uses the systeminformation (SI) generated by radio access node 22, and even in someexample implementations specifically requests certain system information(SI), in an on-demand fashion. To that end, the terminal processor 40 ofwireless terminal 26 is shown as comprising SIB processor 56.

The node processor 30, and system information (SI) generator 54, inparticular, generates a value tag that is associated with the systeminformation (SI). The value tag, also known as a version tag or “Vtag,”is configured to provide an indication of the version or vintage ofsystem information with which the value tag is associated. In someexample implementations the value tag may take the form of a numeral orcharacter, e.g., “1” for the first version, “2” for the second version,etc., or “A” for the first version, “B,” for the second version, etc.Any other convention for differentiating between values or versions mayinstead be employed. To this end, system information (SI) generator 54is shown as comprising value tag generator 57.

The value tag generator 57 serves, e.g., to change the value tag when aparameter of the system information is changed. For example, the valuetag generator 57 may increment a number of the value tag when aparameter of the second type system information is changed.

The system information (SI) generator 54 also comprises SIB deliverycontroller 58, which controls the timing and content of delivery ofsystem information (SI), as well as timing and delivery of certainnode-available system information (“NASI”). In an example embodiment andmode illustrated in FIG. 2, the node-available system informationcomprises a node-available system information message NASIM 59 thatincludes both an identification of the system information that isavailable from the radio access node 22, and the value tag associatedwith that available system information. To this end, the NASIM 59 ofFIG. 2 shows an identification of system information field orinformation element 59A, and a value tag field or information element59B.

FIG. 3 depicts a certain example, representative, basic acts or stepsperformed by the radio access node 22 of FIG. 1. Act 3-1 comprisesgenerating a value tag associated with system information that isavailable at the radio access node 22. As is understood in the art, thesystem information facilitates the use of communication servicesprovided by the access node. Act 3-2 comprises transmitting over theradio interface 24 the node-available system information (“NASI”). Suchtransmission may be by means of the node-available system informationmessage NASIM 59. An arrow 3-2 in FIG. 1 corresponds to act 3-2 (and, inan example implementation, to the node-available system informationmessage NASIM 59). As indicated above and with respect to FIG. 2, thenode-available system information message comprises an identification ofthe system information and the value tag associated with the systeminformation.

FIG. 4 depicts a certain example, representative, basic acts or stepsperformed by the wireless terminal 26 of FIG. 1. Act 4-1 comprisesreceiving, from the radio access node 22, the node-available systeminformation message (3-2) that comprises an identification ofnode-available system information and a node-transmitted value tagassociated with the node-available system information. Act 4-2 comprisesmaking a determination, on the basis of the node-transmitted value tag,whether to request that the node-available system information betransmitted to the wireless terminal. If the determination of act 4-2indicates that the available system information as advertised in thenode-available system information message (3-2) should be obtained(e.g., because that available system information has a more recent valuetag), then the wireless terminal 26 sends a request message to the radioaccess node 22 to obtain the advertised system information.

FIG. 5 illustrates a certain example embodiment and mode wherein systeminformation (SI) is classified into plural categories or types, anddelivery of each category or type of system information (SI) isseparately triggered and thus separately delivered across the radiointerface 24 to one or more wireless terminals. Accordingly, the systeminformation (SI) generator of a radio access node 22 is also known asdifferentiated delivery SIB generator 54.

In view of the fact that, in certain example embodiments and modes, thesystem information (SI) is classified into plural categories or types,the system information (SI) generator 54 is depicted in FIG. 5 ascomprising SIB type classifier 60 that defines the plural categories ortypes of system information, and may further define an associationbetween the plural types and respective system information blocks. Forsake of examples, two representative categories or types of systeminformation (SI) are shown as defined by the SIB type classifier 60 inFIG. 5: a first type of system information (1TYP SIB) and a second typeof system information (2TYP SIB). Definitions and procedures forhandling for the first type of system information (1TYP SIB) and thesecond type of system information (2TYP SIB) may be selectivelyconfigured and maintained, and are accordingly reflected by 1TYPSIBcontroller 62 and 2TYPSIB controller 64, respectively.

In an example embodiment and mode, the first type of system information(1TYP SIB) is SIB “essential system information,” which means systeminformation (SI) which is essential to or minimally required by thewireless terminal 26 for initial access to the radio access network andto the radio interface 24 in particular. Essential system informationmay also be referred to as “minimum system information.” On the otherhand, in the same example embodiment and mode, the second type of systeminformation (2TYP SIB) is non-essential system information (SI).“Non-essential” system information (SI) is defined as all other types ofinformation, and thus excludes the minimal information required forinitial access. As such, the second type of system information (2TYPSIB) may facilitate the utilization of certain features or servicesprovided by or through the radio access node 22. Non-essential systeminformation may also be referred to as “other system information.” Thus,the first type system information comprises information that isperiodically broadcasted by the transmitter and which is required forinitial access to the radio access network, but the second type systeminformation is not required for initial access to the radio accessnetwork.

In some example embodiments and modes described herein, the radio accessnode 22 separately delivers the different types of system information,e.g., delivers the second type of system information (2TYP SIB)separately from the first type of system information (1TYP SIB). Forexample, the node processor 30 may schedule periodic transmissions bythe transmitter of first type system information over the radiointerface; and thereafter or separately from the periodic transmissionsof the first type system information, schedule transmission by thetransmitter of second type system information over the radio interface.Accordingly, in example embodiments and modes, the SIB deliverycontroller 58, among other things, may implement the “differentiated”delivery of the second type of system information (2TYP SIB) apart fromthe first type of system information (1TYP SIB). As explained herein,the transmission of second type system information may be either byunicast or broadcast.

FIG. 5 further illustrates that the wireless terminal 26 may, afterobtaining initial access to the communications system 20 (e.g., as aresult of receiving the first type of system information (1TYP SIB)),recognize or appreciate that the wireless terminal 26 may lack and needthe second type of system information (2TYP SIB). Thus, the wirelessterminal 26 may make a special request for, and receive from the radioaccess node 22, the second type of system information (2TYP SIB). TheFIG. 5 embodiment and mode is thus an example of the radio access node22 providing second type system information “on demand.” Such request ordemand for the second type of system information (2TYP SIB) may arise,for example, when the wireless terminal 26 seeks to utilize a certainservice provided by the communications system 20 or functionality of thewireless terminal 26 which, although not required for access, mayenhance the operation of the wireless terminal 26. Accordingly, FIG. 5shows the SIB processor 56 of the wireless terminal 26 as comprising2TYPSIB request generator 70, which may generate a 2TYPSIB requestdepicted by arrow 5-1.

FIG. 5 further shows node frame/signal scheduler/handler 50 ascomprising 2TYPSIB request handler 72, and further shows the SIBdelivery controller 58 as comprising 2TYPSIB response generator 74. InFIG. 5 embodiment and mode, the 2TYPSIB response generator 74 generatesa response message 5-2 that includes one or more requested systeminformation blocks (SIBs), e.g., includes at least one block of thesecond type system information.

Thus, in FIG. 5 embodiment and mode, the node processor 30 schedulesperiodic transmissions by the transmitter of first type systeminformation over the radio interface. Thereafter or separately from theperiodic transmissions of the first type system information, and uponrequest by the wireless terminal 26, the node processor 30 schedulestransmission by the transmitter of second type system information overthe radio interface. The request by the wireless terminal 26 may ariseafter the wireless terminal 26 receives the node-available systeminformation message NASIM 59, which advises of the value tag for thenode-available system information. Thus, in FIG. 5 embodiment and mode,the value tag is associated with the second type system information.

FIG. 6 shows an example message flow for the embodiment of FIG. 5. InFIG. 6 message flow, when a wireless terminal enters the coverage areaof the radio access node 22, the wireless terminal first receives fromthe radio access node 22 the Essential System Information (i.e., thefirst type of system information (1TYP SIB)), and in particular receivesEssential System Information periodically broadcasted in messagescontaining the essential SIB(s) as information elements. The periodicbroadcast by the radio access node 22 of the Essential SystemInformation is shown by messages 6-1-a and 6-1-b of FIG. 6. It isunderstood (in FIG. 6 and other similar drawings) that there may be morethan two such broadcast messages. An example Essential SystemInformation message for the FIG. 5 embodiment and mode are shown in FIG.7 and hereinafter described.

As shown in FIG. 7, the Essential System Information message maycomprise a nonEssentialSIBInfo information element that includes theidentification of the non-essential SIBs. If the nonEssentialSIBInfoinformation element is not present in the message, or if the informationelement is present but the list is empty, the wireless terminal assumesthat all the SIBs from this radio access node 22 are essential SIBs.

Upon receiving the Essential System Information, i.e., the first type ofsystem information (1TYP SIB), the wireless terminal 26 initiates thesystem access procedure by sending an Access Request message 6-2, whichis acknowledged by the radio access node 22 with an Access Responsemessage 6-3. Following the system access procedure (comprised of theacts just described), the wireless terminal 26 sends a Non-EssentialSystem Information Request message 6-4 to the radio access node 22. TheNon-Essential System Information Request message 6-4 may be generated by2TYP SIB request generator 70 of FIG. 5, and may include an indicationof one or more pieces of the second type of system information (2TYPSIB), e.g., one or more SIB numbers (SIB #), that the wireless terminal26 desires. The wireless terminal 26 was made aware of the existence ofthe second type system information by the nonessentialSIBinfoinformation element. Such an indication of desired SIB # may beexpressed in an information element of the Non-Essential SystemInformation Request message 6-4. The Non-Essential System InformationRequest message 6-4 may be sent using uplink dedicated resources (e.g.,radio resources of a frame).

In response to the Non-Essential System Information Request message 6-4,the radio access node 22 may send Non-Essential System InformationResponse message 6-5 using the downlink dedicated resources. TheNon-Essential System Information Response message 6-5 comprises therequested SIB #n (e.g., the SIB #n requested by the wireless terminal26). The requested SIB #n may be included in an information element ofthe Non-Essential System Information Response message 6-5. Afterward,when the wireless terminal 26 has successfully obtained the requestedSIB #n from the Non-Essential System Information Response message 6-5,the wireless terminal 26 may send to the radio access node 22 aNon-Essential System Information Completion message 6-6, at which pointthe radio access node 22 may release the uplink/downlink dedicatedresources. Alternatively, the radio access node 22 may release theuplink/downlink dedicated resources after sending Non-Essential SystemInformation Response message 6-5.

An example Essential System Information message for the FIG. 5embodiment and mode is shown in FIG. 7. In the embodiment and mode ofFIG. 5 and FIG. 6, one or more, and preferably a non-essential (e.g.,second type) SIB is associated with a value tag that uniquely identifiesa specific version of the content for that SIB. When broadcastingEssential System Information message, the radio access node 22 of FIG. 5includes the value tags for the latest contents of non-essential SIBs.Further, the value tag changes when any configuration parameters in thecorresponding SIB gets updated. In one example implementation, the valuetag is incremented by one upon the SIB update. Other types ofmodifications, e.g., decrementation, version prefixes or suffixes, maybe employed.

FIG. 7 shows an example format of the Essential System Informationmessage, wherein in the nonEssentialSIBInfo information element eachsibId is paired with valueTag, the value tag of the correspondingnon-essential SIB. Thus, in an example implementation, thenode-available system information message NASIM 59 may be an EssentialSystem Information message, as shown in FIG. 7. FIG. 7 particularlyshows that the Essential System Information message may also, whenfunctioning as the node-available system information message NASIM 59,include an information element specifying what non-essential SIBs areavailable at this radio access node 22 upon request. FIG. 7 shows theessentialSystemInformation information element carrying at least oneessential SIB, and a nonEssentialSIBInfo information element may includea list of identifiers (sibId's) for such available non-essential SIBs.In addition, for one or more and preferably each non-essential SIBs, avalue tag is provided in the nonEssentialSIBInfo information element.

FIG. 7 also shows that Essential SIB(s) may also be associated with atleast one value tag, which is different from the ones for non-essentialSIBs, and may be conveyed as a part of the Essential System Informationmessage.

In a certain example, embodiments and modes, the value tag of anon-essential SIB may be valid within one radio access node 22, e.g.,valid within a coverage area or cell served by the radio access node 22.But in other example embodiments and modes, the value tag may havecollective applicability, e.g., be capable of expressing a value formore than one cell, for more than one piece of system information (e.g.,more than one SIB), etc. In other words, the applicable “base” of thevalue tag, the information to which the value tag pertains, may beselectively defined in terms of various factors such as area, number ofSIBs, and so forth.

In the above regard, in an example embodiment and mode shown in FIG. 8,the system information (SI) generator 54 includes not only the value taggenerator 57, but also logic, memory, or controller for a value tag basedefinition 80. In an example implementation, for example, the value tagbase definition 80 may specify that the value tag is valid in at leastone geographical area comprising a plurality of radio access nodes.Thus, the node processor 30 may generate the value tag to be valid in ageographical area served by the access node and a group of at least oneother access node. In such example implementation, the value tag basedefinition 80, or value tag “validity area,” may be separately signaledfrom the radio access nodes to the wireless terminals in theirrespective coverage areas. That is, the node processor 30 may generate asignal (such as signal 8-1 of FIG. 8) to define the group of otheraccess nodes.

Thus, in FIG. 8 embodiment and mode, a wireless terminal may considerthe non-essential system information, a second type SIB, to be “current”if (1) it was received in the validity area of the radio access nodeupon which the wireless terminal is camping; (2) the value tag of thereceived non-essential SIB is the same as the one that the camped radioaccess node is currently advertising in the Essential System Informationmessage, and (3) it was received within a pre-determined ornetwork-configured (e.g., configured by eNB) time period from thepresent time.

FIG. 9 shows an example message flow for the example embodiment and modeof FIG. 8. In the example embodiment and mode of FIG. 8 it is assumedthat the wireless terminal 26 makes an on-demand request for second typesystem information (SI). Accordingly, in FIG. 9, the Essential SystemInformation messages 9-1 a and 9-1 b are indicated as being “SIB #n:on-demand.” Further, as explained above, the Essential SystemInformation messages 9-1 a and 9-1 b may include the value tag(“valueTag: m”). After receiving the Essential System Information, thewireless terminal 26 may perform an access procedure comprising AccessRequest message 6-2 and Access Response message 6-3.

In FIG. 9 scenario, the wireless terminal 26 may not need to takefurther actions respecting the second type of system information if thewireless terminal 26 has previously received the SIB #n and the valuetag for the previously-received SIB #n as stored at the wirelessterminal 26 is current (e.g., is “m”). Otherwise, if the wirelessterminal 26 has a value tag for the SIB #n that is older than “m,” thewireless terminal 26 may proceed to request the SIB #n transmissionusing the Non-Essential System Information Request message 6-4, in amanner similar to that described in a previous embodiment.

Thus, in the example embodiment and mode of FIG. 8 and FIG. 9, theNon-Essential System Information Response message 9-5 and/orNon-Essential System Information Completion message 9-6 may contain thevalue tag with the current value (valueTag=m).

In an example embodiment and mode shown in FIG. 10, the wirelessterminal 26 may optionally include in request message 10-1 (requestingthe second type system information) the stored value tags of therequested second type system information. This may occur in a situationin which the wireless terminal 26 already has stored values for thesecond type system information and already has stored value tags for thestored second type system information, but the wireless terminal 26 doesnot know if the stored second type system information is or is not trulycurrent in terms of network usage for each of the stored SIBs of thesecond type system information. The wireless terminal 26 may requestsecond type system information for plural different second type systeminformation SIBs, and the plural second type system information SIBs mayeach have different value tags.

In the example embodiment and mode of FIG. 10, the wireless terminal 26comprises value tag inserter functionality 84, which includes in therequest message 10-1 the stored value tag for the second type systeminformation already stored at the wireless terminal 26. Moreover, asunderstood below, the radio access node 22 and SIB delivery controller58, in particular, may comprise a compression formatter for the secondtype system information, e.g., 2TYPSIB compression formatter 86.

Thus, the FIG. 10 example embodiment and mode are similar to theembodiment and mode of FIG. 8, but the wireless terminal 26 mayoptionally include in the Non-Essential System Information Requestmessage 10-1 the value tags of the requested non-essential SIBs, wherethe wireless terminal 26 obtained those value tags when it previouslyreceived the corresponding non-essential SIBs.

An exemplary scenario of the FIG. 10 embodiment and mode is illustratedin the message flow of FIG. 11. FIG. 11 shows, by the Non-EssentialSystem Information Request message 11-4 (which corresponds to message10-1 of FIG. 10), that valueTag=k for its requested SIB #n. Based onthis received value tag, the radio access node 22 and the 2TYPSIBcompression formatter 86 in particular may compose the “compressed”content of the SIB #n to be delivered via Non-Essential SystemInformation Response message 11-5. The wireless terminal 26 may send tothe radio access node 22 a Non-Essential System Information Completionmessage 11-6.

In one example implementation of FIG. 10 and FIG. 11, the compressedcontent comprises the differences between the current SIB #n(valueTag=m) and the previously transmitted (valueTag=k). For example,if SIB #n consists of parameters p1 to p10 and if only p3 and p7 havebeen updated (if the radio access node 22 has newer values only forparameters p3 and p7 of second type system information), the compressedcontent of the Non-Essential System Information Response message 11-5may include only p3 and p7 with updated values.

Thus the example embodiment and mode of FIG. 10 and FIG. 11 isparticularly but not exclusively applicable to situations in which thesecond type system information comprises plural parameters, and thereceiver is configured to receive a wireless terminal-reported value tagin the request message. Basic example acts performed by the radio accessnode 22 in conjunction with the example embodiment and mode of FIG. 10and FIG. 11 are shown in FIG. 12. Act 12-1 comprises the node processor30 (and system information (SI) generator 54 in particular) changing thevalue tag when at least one of the plural parameters of the second typesystem information changes and storing a parameter identifier for the atleast one of the plural parameters for which content changes. Act 12-2comprises making a comparison of the wireless terminal-reported valuetag (e.g., the value tag reported in the request message 10-1) with thevalue tag (the changed value tag). Act 12-3 comprises preparing theresponse message (e.g., the Non-Essential System Information Responsemessage 11-5) to include only changed ones of the plural parametersbased on the comparison of the value tag relative to the wirelessterminal-reported value tag.

In some cases, the radio access node 22 may have an option to send thenon-compressed versions of the requested non-essential SIBs even if theNon-Essential System Information Request message contains value tags.One example of such cases is when the radio access node 22 no longerstores the contents of the previously transmitted non-essential SIBsindicated by the received value tags.

Basic example acts performed by the wireless terminal 26 in conjunctionwith the example embodiment and mode of FIG. 10 and FIG. 11 are shown inFIG. 13. Act 13-1 comprises the wireless terminal 26 transmitting theterminal-stored value tag in the request message (e.g., in message11-4). Act 13-2 comprises the wireless terminal 26 receiving theresponse message (e.g., message 11-5) from the access node. As mentionedabove, the response message includes changed ones of the pluralparameters based on a comparison at the access node of the node-reportedvalue tag relative to the terminal-stored value tag. Act 13-3 comprisesthe wireless terminal 26 using the changed ones of the plural parametersof the system information to replace corresponding parameters of theterminal-stored system information.

In the above regard, the wireless terminal 26 may construct the entireSIB #n using the received compressed content, and the content of SIB #nsaved in its memory. In the example described above, the wirelessterminal 26 may overwrite saved p3 and p7 with the ones received in thecompressed content. The wireless terminal 26 may further update thesaved value tag for SIB #n to valueTag=m.

In typical deployments, the content of system information is stable, andeven if it has some updates, those updates are generally minor. By theapproach described in the example embodiment of FIG. 10 and FIG. 11, itis possible to reduce the data size of the Non-Essential SystemInformation Response message.

The example embodiment and mode of FIG. 14 is similar to the embodimentand mode of FIG. 8, but differs in that a value tag may represent avalue or version for an aggregation of multiple non-essential SIBs,e.g., a group of second type system information blocks. In particular,the value tag base definition 80(14) of the embodiment and mode of FIG.14 defines multiple sibIds associated with one valueTag to thereby forma non-essential or second type system information SIB “group.” Thus, inthe example embodiment and mode of FIG. 14, the node processor 30generates the value tag to be associated with a group of plural secondtype system information blocks. The 2TYP SIB request generator 70 of thewireless terminal 26 of FIG. 14 includes a group identifier inserter(“group ID inserter 88”) that includes, in a request message 14-1, anidentification of the group of second type system information blockswhich are the subject of a second type system information request. Therequest message 14-1 also may include a value tag associated with thegroup.

FIG. 15 shows an example format of the Essential System Informationmessage, where multiple sibIds associated with one valueTag forms anon-essential SIB group. The valueTag in each non-essential SIB group ofthis message is updated when the content of at least one non-essentialSIB belonging to this group changes. In one configuration, eachnon-essential SIB group may be associated with groupId, an index of thegroup in the order of occurrence in the nonEssentialSIBInfo.

FIG. 16 illustrates an example message flow for the embodiment and modeof FIG. 14. FIG. 16 particular shows Essential System Informationmessages 16-1 a and 16-1 b as advertising a non-essential SIB group withgroupId=a and valueTag=m. The wireless terminal 26, when requesting thecontents of the non-essential SIBs belonging to the group, sends to theradio access node 22 the Non-Essential System Information Requestmessage 16-4 containing groupId=a. In response, the radio access node 22sends Non-Essential System Information Response message 16-5 includingthe contents of all the non-essential SIBs of the group defined bygroupId=a. The wireless terminal 26 may send to the radio access node 22a Non-Essential System Information Completion message 16-6.

As explained above, the example embodiment and mode of FIG. 14 and FIG.16 involves, e.g., generating the value tag to be associated with agroup of plural second type system information blocks. Basic exampleacts performed by the radio access node 22 in conjunction with theexample embodiment and mode of FIG. 14 and FIG. 16 are shown in FIG. 17.Act 17-1 comprises changing the value tag when content changes for atleast one block of the group and storing a block identifier for the atleast one block for which content changes. Act 17-2 comprises receivinga wireless terminal-reported value tag in the request message. Act 17-3comprises making a comparison of the wireless terminal-reported valuetag with the value tag. Act 17-4 comprises preparing the responsemessage to include only changed ones of the plural blocks of the groupbased on the comparison of the value tag relative to the wirelessterminal-reported value tag.

Basic example acts performed by the wireless terminal 26 in conjunctionwith the example embodiment and mode of FIG. 14 and FIG. 16 are shown inFIG. 18. Act 18-1 comprises transmitting an identification of a group ofsecond type system information blocks and the associated value tag inthe request message (e.g., in message 16-4 of FIG. 16). Act 18-2comprises receiving the response message (e.g., message 16-5 of FIG. 16)from the access node, the response message including changed ones of theplural blocks of the group based on the comparison of thenode-transmitted value tag relative to the terminal-stored value tag.Act 18-3 comprises using the changed ones of the plural blocks of thegroup of the system information to replace corresponding blocks of theterminal-stored system information.

Another example embodiment and mode, having a message flow representedby FIG. 19, is based on the combination of the content compressionmethod disclosed in the embodiment of FIG. 10 and the concept ofnon-essential SIB group described in the embodiment of FIG. 14. In themessage flow of FIG. 19, the wireless terminal 26 sends Non-EssentialSystem Information Request message 19-4 with groupId=a, since the valuetag that UE saves for this non-essential SIB group is not current. TheNon-Essential System Information Response message 19-5 that the radioaccess node 22 sends in response contains compressed content of thenon-essential SIB group. In one implementation, the compressed contentcomprises the differences between the current non-essential SIBs (valueTag=m) and the previously broadcasted non-essential SIBs(valueTag=k)under the same non-essential SIB group. The wireless terminal 26 maysend to the radio access node 22 a Non-Essential System InformationCompletion message 19-6.

FIG. 20 illustrates another signaling message flow for another exampleembodiment and mode. The initial messages (e.g., the Essential SystemInformation messages 20-1 a and 20-1 b, the Access Request 20-2 and theAccess Response 20-3) of FIG. 20 are similar to those of some precedingembodiments and modes, but in FIG. 20 the Non-Essential SystemInformation Response message 20-5 includes an information elementindicating that the requested SIB #n will be broadcasted instead ofbeing unicasted. The radio access node 22, at a subsequent cycle of anEssential System Information message transmission (e.g., at theEssential System Information message 20-6 a), starts including at leastone information element for the schedule of SIB #n transmissions. Basedon this schedule information, the radio access node 22 broadcasts theNon-Essential System Information message 20-7 a containing the requestedSIB #n. As indicated by the messages depicted in broken lines in FIG.20, the radio access node 22 may repeat these two steps multiple timesfor reliable delivery (e.g., the Essential System Information message20-6 b and the Non-Essential System Information Message 20-7 b). Byreceiving at least one of these repetitions, the wireless terminal 26should successfully obtain the SIB #n. The number of repetitions may bedetermined by the radio access node 22, and information indicating thenumber may be broadcasted together with the essential systeminformation. Alternatively, the number of repetitions may be determinedby the wireless terminal 26 and may be notified to the radio access node22 through the Non-Essential System Information Request message 20-4.

A benefit of the FIG. 20 embodiment and mode is that the requested SIB#n may also be received by other wireless terminals entering the samecoverage area. Such wireless terminals may receive the Essential SystemInformation message 20-6 a and know that the SIB #n is scheduled to betransmitted. As a result, the number of transmissions for Non-EssentialSystem Information Request message 20-4 may be reduced. An additionalbenefit is that the transmissions of messages 20-2 and 20-3 may also bereduced.

FIG. 21 illustrates yet another signaling message flow for anotherexample embodiment and mode. The initial messages (e.g., the Essentialsystem Information messages 21-1 a and 21-1 b, the Access Requestmessage 21-2, and the Access Response 21-3) of FIG. 21 are similar tothose of some preceding embodiments and modes, but in FIG. 21 thebroadcasts of SIB #n in the Non-Essential System Information message(s)occur on pre-determined resource allocations. For example, thepre-determined resource allocations may be defined by using aperiodicity and/or an offset. The radio access node 22 may optionallyrepeat sending Non-Essential System Information message(s) at multipleoccasions (e.g., the Non-Essential System Information messages 21-6 aand 21-6 b). The wireless terminal 26 that has sent a Non-EssentialSystem Information Request message 21-4, requesting the SIB #n, mayreceive Non-Essential System Information on at least one pre-determinedradio resource allocation, without receiving an Essential SystemInformation message. The wireless terminal 26 may also receive theNon-Essential Information Response 21-5 from the access node 22. Theradio access node 22 may use these allocated resources for otherpurposes if it does not transmit SIB #n.

In the embodiment and mode of FIG. 21, any other wireless terminalsentering the coverage first receives the Essential System Informationmessage 21-1 a, then it may monitor pre-determined resources for severaltimes before sending Non-Essential System Information Request message21-4, in order to suppress unnecessary transmissions of Non-EssentialSystem Information Request message. The number of monitoring trials maybe pre-determined, or may be configured by the Essential SystemInformation message.

In addition, in the embodiment and mode of FIG. 21, the pre-determinedresource allocations can be configurable by including the information ofallocations in Essential System Information messages 21-1 a and 21-1 b.The pre-determined resource allocations of a given non-essential SIB maybe jointly coded with whether the non-essential SIB is available at thisradio access node by request. Alternatively, the pre-determined resourceallocations may be tied to the SIB indices.

FIG. 22 illustrates yet another signaling message flow for anotherexample embodiment and mode. In FIG. 22, the wireless terminal 26receives the Essential System Information message(s) (e.g., theEssential Systems Information messages 22-1 a and 22-1 b) from the radioaccess node 22. The Access Request message(s) 22-2 contain(s) a requestfor the SIB #n broadcast. The radio access node that receives therequest may decide to deliver the SIB #n by unicast, or by broadcast. Incase of unicast, it includes an information element of unicastindication for SIB #n in the Access Response message 22-3, as shown inFIG. 22. Additionally, the wireless terminal 26 may transmit aNon-Essential System Information Request message 22-4 to the radioaccess node 22 and receive a Non-Essential System Information Response22-5 from the radio access node 22. In another example, the radio accessnode 22 includes an information element of a broadcast indication forSIB #n in Access Response message 23-3, as shown in FIG. 23.Additionally, in FIG. 23, the wireless terminal may receive theEssential System Information message(s) (e.g., the Essential SystemInformation messages 23-1 a and 23-1 b) from the radio access node 22and transmit an Access Request message 23-2 to the radio access node 22.The wireless terminal 26 may receive an Access Reponse message 23-3 fromthe radio access node 22. The wireless terminal 26 may further receiverEssential System Information message(s) (e.g., the Essential Systeminformation messages 23-6 a and 23-6 b) and Non-Essential Systeminformation message(s) (e.g., the Non-Essential System informationmessages 23-7 a and 23-7 b) from the radio access node 22. Analternative approach to FIG. 23 is shown in FIG. 24, where Non-EssentialSystem Information message(s) (e.g., the Non-Essential SystemInformation messages 24-7 a and 24-7 b) is broadcasted on pre-determinedresource allocations. Additionally, in FIG. 24, the wireless terminal 26may receive the Essential System Information message(s) (e.g., theEssential System Information messages 24-1 a and 24-1 b) from the radioaccess node 22 and transmit an Access Request message 24-2 to the radioaccess node 22. The wireless terminal 26 may receive an Access Reponsemessage 24-3 from the radio access node 22. The wireless terminal 26 mayfurther receive Essential System Information message(s) (e.g., theEssential System information messages 24-6 a and 24-6 b) andNon-Essential System information message(s) e.g., the Non-essentialinformation messages 24-7 a and 24-7 b) from the radio access node 22.

Further information regarding the technology disclosed herein, includingbut not limited to the example embodiments and modes of FIG. 20-FIG. 24,is provided in related U.S. Provisional Application 62/367,447, entitled“ON-DEMAND SYSTEM INFORMATION FOR WIRELESS TELECOMMUNICATIONS,” filed onJul. 27, 2016.

Certain units and functionalities of the radio access node 22 andwireless terminal 26 are, in example embodiments, implemented byelectronic machinery, computer, and/or circuitry. For example, the nodeprocessors 30 and terminal processors 40 of the example embodimentsherein described and/or encompassed may be comprised by the computercircuitry of FIG. 25. FIG. 25 shows an example of such electronicmachinery or circuitry, whether node or terminal, as comprising one ormore processor(s) circuits 140, program instruction memory 142; othermemory 144 (e.g., random access memory (RAM), cache, etc.); input/outputinterfaces 146; peripheral interfaces 148; support circuits 149; andbusses 150 for communication between the aforementioned units.

The program instruction memory 142 may comprise coded instructionswhich, when executed by the processor(s), perform acts including but notlimited to those described herein. Thus, it is understood that each ofnode processor 30 and terminal processor 40, for example, comprisememory in which non-transient instructions are stored for execution.

The memory 144, or computer-readable medium, may be one or more ofreadily available memory such as RAM, read only memory (ROM), floppydisk, hard disk, flash memory or any other form of digital storage,local or remote, and is preferable of non-volatile nature. The supportcircuits 149 are coupled to the processors 140 for supporting theprocessor in a conventional manner. These circuits include cache, powersupplies, clock circuits, input/output circuitry and subsystems, and thelike.

The technology of this application thus encompasses but is not limitedto the following example embodiments, example features, and exampleadvantages:

Example Embodiment 1

A user equipment (UE) for receiving system information, comprising:

a processor;

a memory in electronic communication with the processor, whereininstructions stored in the memory are executable to:

-   -   receive first system information periodically broadcasted from        eNB;    -   determine types of second system information to additionally        receive, wherein each of said types corresponds to a second        system information block;    -   transmit to the eNB a request containing said types of the        second system information; and,    -   receive the requested second system information from the eNB;

Example Embodiment 2

The UE of Example Embodiment 1, wherein contents of one or plurality ofsecond system information blocks are associated with a value tag.

Example Embodiment 3

The UE of Example Embodiment 2, wherein said value tag is assigned andused separately from one or more value tags used for the first systeminformation.

Example Embodiment 4

The UE of Example Embodiment 2, wherein said value tag is valid withinone eNB.

Example Embodiment 5

The UE of Example Embodiment 2, wherein said value tag is valid withinat least one geographical area consisting of a plurality of eNBs.

Example Embodiment 6

The UE of Example Embodiment 2, wherein said value tag is valid within apre-determined or network-configured time period from the time whereinthe UE receives the associated second system information blocks.

Example Embodiment 7

The UE of Example Embodiment 2, wherein from said first systeminformation the UE obtains value tags, each of which indicates thecurrent version of the corresponding second system information blocks.

Example Embodiment 8

The UE of Example Embodiment 7, wherein the second system informationblocks associated with a same value tag are identified by a group index.

Example Embodiment 9

The UE of Example Embodiment 8, wherein said group index is used in saidrequest containing said types of the second system information.

Example Embodiment 10

The UE of Example Embodiment 7, wherein the UE saves in its memory thereceived second system information blocks and their associated valuetags.

Example Embodiment 11

The UE of Example Embodiment 10, wherein the UE determines whether theUE transmits to the eNB a request for delivery of one or a plurality ofsecond system information blocks by comparing each of the current valuetags included in said first system information and, if present, thesaved value tag corresponding the same second system information blocks.

Example Embodiment 12

The UE of Example Embodiment 11, wherein the UE refrains from requestingdelivery of second system information blocks if the current value tagfor these second system information blocks matches the saved value tagfor the same second system information blocks.

Example Embodiment 13

The UE of Example Embodiment 10, wherein the UE includes the saved valuetags in said request.

Example Embodiment 14

The UE of Example Embodiment 13, wherein the UE receives from the eNBone or a plurality of compressed contents, each of which is a compressedimage of one or a plurality of second system information blocks.

Example Embodiment 15

The UE of Example Embodiment 14, wherein each of said compressedcontents is produced based on two versions of the same types of secondsystem information with different value tags.

Example Embodiment 16

The UE of Example Embodiment 15, wherein each of said compressedcontents consists of differences between said two versions.

Example Embodiment 17

The UE of Example Embodiment 14, wherein the UE constructs one or aplurality of second system information blocks using the compressedcontents and the saved second system information blocks.

Example Embodiment 18

The UE of Example Embodiment 10, wherein upon receiving a second systeminformation block the UE updates the corresponding value tag saved inthe memory.

Example Embodiment 19

An evolved node B (eNB) for delivering system information, comprising:

a processor;

a memory in electronic communication with the processor, whereininstructions stored in the memory are executable to:

-   -   periodically broadcast first system information that includes        types of second system information available by request, wherein        each of said types corresponds to a second system information        block;    -   receive from a UE a request for transmission of said second        system information; and,    -   transmit said requested second system information.

Example Embodiment 20

The eNB of Example Embodiment 19, wherein contents of one or a pluralityof second system information blocks are associated with a value tag.

Example Embodiment 21

The eNB of Example Embodiment 20, wherein said value tag is assigned andused separately from one or more value tags used for the first systeminformation.

Example Embodiment 22

The eNB of Example Embodiment 20, wherein said value tag is valid withinone eNB.

Example Embodiment 23

The eNB of Example Embodiment 20, wherein said value tag is valid withina geographical area consisting of a plurality of eNBs.

Example Embodiment 24

The eNB of Example Embodiment 20, wherein said value tag is valid withina pre-determined or network-configured time period from the time whereinthe UE receives the associated second system information blocks.

Example Embodiment 25

The eNB of Example Embodiment 20, wherein the eNB includes in said firstsystem information value tags, each of which indicates the currentversion of the corresponding second system information blocks.

Example Embodiment 26

The eNB of Example Embodiment 25, wherein the second system informationblocks associated with a same value tag are identified by a group index.

Example Embodiment 27

The eNB of Example Embodiment 20, wherein the eNB generates one or aplurality of compressed contents for second system information uponreceiving said request from the UE.

Example Embodiment 28

The eNB of Example Embodiment 27, wherein the eNB receives in saidrequest at least one identification identifying at least one secondsystem information block to deliver to the UE.

Example Embodiment 29

The eNB of Example Embodiment 28, wherein the identification is a valuetag.

Example Embodiment 30

The eNB of Example Embodiment 28, wherein the identification is a groupindex.

Example Embodiment 31

The eNB of Example Embodiment 27, wherein each compressed content isproduced based on the version of the second system information block(s)associated with the received identification and the current version ofthe same second system information block(s).

Example Embodiment 32

The eNB of Example Embodiment 31, wherein each of said compressedcontent consists of differences between said two versions.

Example Embodiment 33

A method for a user equipment (UE) comprising:

receiving first system information periodically broadcasted from eNB;

determining types of second system information to additionally receive;

transmitting to the eNB a request containing said types of the secondsystem information, wherein each of said types corresponds to a secondsystem information block; and,

receiving the requested second system information from the eNB.

Example Embodiment 34

A method for an evolved node B (eNB) comprising:

periodically broadcasting first system information that includes typesof second system information available by request;

receiving from a UE a request for transmission of said second systeminformation, wherein each of said types corresponds to a second systeminformation block; and,

transmitting said requested second system information.

Example Embodiment 35

In one of its example aspects, the technology disclosed herein concernsan access node of a radio access network. The access node comprisesprocessor circuitry and a transmitter. The processor circuitry isconfigured to generate a value tag associated with system information.The system information facilitates the use of communication servicesprovided by the access node. The transmitter is configured to transmit,over a radio interface, node-available system information comprising anidentification of the system information and the value tag associatedwith the system information.

Example Embodiment 36

The node of Example Embodiment 35, wherein the processor circuitry isconfigured: to schedule periodic transmissions by the transmitter offirst type system information over the radio interface; separately fromthe periodic transmissions of the first type system information, toschedule transmission by the transmitter of second type systeminformation over the radio interface. The value tag is associated withthe second type system information.

Example Embodiment 37

The node of Example Embodiment 36, wherein the first type systeminformation is periodically broadcasted by the transmitter and isrequired for initial access to the radio access network, and the secondtype system information is not required for initial access to the radioaccess network.

Example Embodiment 38

The node of Example Embodiment 35, wherein the processor circuitry isconfigured to schedule periodic transmissions by the transmitter offirst type system information over the radio interface, the periodtransmissions also including the node-available system information forsecond type system information, the value tag being associated with thesecond type system information.

Example Embodiment 39

The node of Example Embodiment 38, wherein the processor circuitry isfurther configured to schedule a transmission by the transmitter overthe radio interface of the second type system information separatelyfrom the periodic transmissions of the first type system information.

Example Embodiment 40

The node of Example Embodiment 38, wherein the processor circuitry isconfigured to change the value tag when a parameter of the second typesystem information is changed.

Example Embodiment 41

The node of Example Embodiment 40, wherein the processor circuitry isconfigured to increment a number of the value tag when a parameter ofthe second type system information is changed.

Example Embodiment 42

The node of Example Embodiment 38, wherein the processor circuitry isconfigured to generate the value tag to be valid in a cell served by theaccess node.

Example Embodiment 43

The node of Example Embodiment 38, wherein the processor circuitry isconfigured to generate the value tag to be valid in a geographical areaserved by the access node and a group of at least one other access node.

Example Embodiment 44

The node of Example Embodiment 43, wherein the processor circuitry isconfigured to generate a signal to define the group of other accessnodes.

Example Embodiment 45

The node of Example Embodiment 35, wherein the access node furthercomprises a receiver configured to receive a request message from awireless terminal when the wireless terminal requests the second typesystem information; and the processor circuitry is configured to includerequested second type system information in a response message to thewireless terminal.

Example Embodiment 46

The node of Example Embodiment 45, wherein the processor circuitry isconfigured to include the value tag in the response message to thewireless terminal.

Example Embodiment 47

The node of Example Embodiment 45, wherein the second type systeminformation comprises plural parameters, the receiver is configured toreceive a wireless terminal-reported value tag in the request message,and the processor circuitry is configured: to change the value tag whenat least one of the plural parameters of the second type systeminformation changes and to store a parameter identifier for the at leastone of the plural parameters for which content changes; to make acomparison of the wireless terminal-reported value tag with the valuetag, and, to prepare the response message to include only changed onesof the plural parameters based on the comparison of the value tagrelative to the wireless terminal-reported value tag.

Example Embodiment 48

The node of Example Embodiment 38, wherein the processor circuitry isconfigured to generate the value tag to be associated with a group ofplural second type system information blocks.

Example Embodiment 49

The node of Example Embodiment 48, wherein the receiver is configured toreceive a wireless terminal-reported value tag in the request message,and the processor circuitry is configured: to change the value tag whencontent changes for at least one block of the group and to store a blockidentifier for the at least one block for which content changes; to makea comparison of the wireless terminal-reported value tag with the valuetag, and, to prepare the response message to include only changed onesof the plural blocks of the group based on the comparison of the valuetag relative to the wireless terminal-reported value tag.

Example Embodiment 50

The node of Example Embodiment 49, wherein at least one of the blocks ofthe group of the second type system information comprises pluralparameters, and the processor circuitry is further configured to preparethe response message to include only changed ones of the pluralparameters of the changed ones of the plural blocks of the group basedon a comparison of the changed in the value tag relative to the wirelessterminal-reported value tag.

Example Embodiment 51

The node of Example Embodiment 45, wherein the processor circuitry isconfigured to include in the response message an indication that therequested system information will be broadcast.

Example Embodiment 52

In another of its example aspects, the technology disclosed hereinconcerns a method in an access node of a radio access network. In abasic implementation the method comprises generating a value tagassociated with system information, the system information facilitatingthe use of communication services provided by the access node; and,transmitting over a radio interface node-available system informationcomprising an identification of the system information and the value tagassociated with the system information.

Example Embodiment 53

The method of Example Embodiment 52, wherein the method furthercomprises: scheduling periodic transmissions by the transmitter of firsttype system information over the radio interface; separately from theperiodic transmissions of the first type system information, schedulingtransmission of second type system information over the radio interfaceto the at least one wireless terminal; and wherein the value tag isassociated with the second type system information.

Example Embodiment 54

The method of Example Embodiment 53, wherein the first type systeminformation is periodically broadcasted by the transmitter and isrequired for initial access to the radio access network, and the secondtype system information is not required for initial access to the radioaccess network.

Example Embodiment 55

The method of Example Embodiment 52, wherein the method furthercomprises scheduling periodic transmissions of first type systeminformation over the radio interface, the period transmissions alsoincluding the node-available system information for second type systeminformation, the value tag being associated with the second type systeminformation.

Example Embodiment 56

The method of Example Embodiment 55, wherein the method furthercomprises scheduling a transmission over the radio interface of thesecond type system information separately from the periodictransmissions of the first type system information.

Example Embodiment 57

The method of Example Embodiment 55, wherein the method furthercomprises changing the value tag when a parameter of the second typesystem information is changed.

Example Embodiment 58

The method of Example Embodiment 57, wherein the method furthercomprises incrementing a number of the value tag when a parameter of thesecond type system information is changed.

Example Embodiment 59

The method of Example Embodiment 52, wherein the method furthercomprises generating the value tag to be valid in a cell served by theaccess node.

Example Embodiment 60

The method of Example Embodiment 52, wherein the method furthercomprises generating the value tag to be valid in a geographical areaserved by the access node and a group of at least one other access node.

Example Embodiment 61

The method of Example Embodiment 60, wherein the method furthercomprises generating a signal which defines the group of other accessnodes.

Example Embodiment 62

The method of Example Embodiment 52, wherein the method furthercomprises receiving a request message from a wireless terminal when thewireless terminal requests the second type system information; andincluding requested second type system information in a response messageto the wireless terminal.

Example Embodiment 63

The method of Example Embodiment 62, wherein the method furthercomprises including the value tag in the response message to thewireless terminal.

Example Embodiment 64

The method of Example Embodiment 62, wherein the second type systeminformation comprises plural parameters, and the method furthercomprises: receiving a wireless terminal-reported value tag in therequest message, changing the value tag when at least one of the pluralparameters of the second type system information changes and storing aparameter identifier for the at least one of the plural parameters forwhich content changes; making a comparison of the wirelessterminal-reported value tag with the value tag, and, preparing theresponse message to include only changed ones of the plural parametersbased on the comparison of the value tag relative to the wirelessterminal-reported value tag.

Example Embodiment 65

The method of Example Embodiment 55, wherein the method furthercomprises generating the value tag to be associated with a group ofplural second type system information blocks.

Example Embodiment 66

The method of Example Embodiment 65, wherein the method furthercomprises receiving a wireless terminal-reported value tag in therequest message, changing the value tag when content changes for atleast one block of the group and storing a block identifier for the atleast one block for which content changes; making a comparison of thewireless terminal-reported value tag with the value tag, and, preparingthe response message to include only changed ones of the plural blocksof the group based on the comparison of the value tag relative to thewireless terminal-reported value tag.

Example Embodiment 67

The method of Example Embodiment 66, wherein at least one of the blocksof the group of the second type system information comprises pluralparameters, and the method further comprises preparing the responsemessage to include only changed ones of the plural parameters of thechanged ones of the plural blocks of the group based on a comparison ofthe changed in the value tag relative to the wireless terminal-reportedvalue tag.

Example Embodiment 68

The method of Example Embodiment 62, wherein the method furthercomprises including in the response message an indication that therequested system information will be broadcast.

Example Embodiment 69

In another of its aspects, the technology disclosed herein concerns awireless terminal which communicates over a radio interface with anaccess node of a radio access network. The wireless terminal basicallycomprises a receiver and processor circuitry. The receiver is configuredto receive from the access node a system information availabilitymessage comprising an identification of node-available systeminformation and a node-transmitted value tag associated with thenode-available system information. The processor circuitry is configuredon the basis of the node-transmitted value tag to determine whether torequest that the node-available system information be transmitted to thewireless terminal.

Example Embodiment 70

The wireless terminal of Example Embodiment 69, wherein the processorcircuitry is configured to make a determination that terminal-storedsystem information is current system information if a terminal-storedvalue tag associated with the terminal-stored system information is thesame as the node-transmitted value tag associated with thenode-available system information.

Example Embodiment 71

The wireless terminal of Example Embodiment 70, wherein the processorcircuitry is configured to make a determination that the terminal-storedsystem information is the current system information if theterminal-stored system information has been received within apredetermined time from a current time.

Example Embodiment 72

The wireless terminal of Example Embodiment 70, wherein the processorcircuitry is configured to make a determination that the terminal-storedsystem information is the current system information if theterminal-stored system information is received in a validity area of theaccess node upon which the wireless terminal is camping.

Example Embodiment 73

The wireless terminal of Example Embodiment 69, wherein the processorcircuitry is configured to make a comparison of terminal-stored valuetag and the node-transmitted value tag and on the basis of thecomparison to generate a request message to request that thenode-available system information be transmitted to the wirelessterminal; and wherein the wireless terminal further comprises atransmitter configured to transmit the request message to the accessnode.

Example Embodiment 74

The wireless terminal of Example Embodiment 73, wherein the processorcircuitry is further configured to use the node-available systeminformation to replace the terminal-stored system information.

Example Embodiment 75

The wireless terminal of Example Embodiment 73, wherein the receiver isconfigured: to receive periodic transmissions of first type systeminformation over the radio interface; separately from the periodictransmissions of the first type system information, to receivetransmission of second type system information over the radio interface;and wherein the node-transmitted value tag is associated with the secondtype system information.

Example Embodiment 76

The wireless terminal of Example Embodiment 75, wherein the first typesystem information comprises information which is periodicallybroadcasted by the transmitter and which is required for initial accessto the radio access network, and where in the second type systeminformation is not required for initial access to the radio accessnetwork.

Example Embodiment 77

The wireless terminal of Example Embodiment 73, wherein the receiver isconfigured to receive periodic transmissions of first type systeminformation over the radio interface, the period transmissions alsoincluding the node-available system information for second type systeminformation, the value tag being associated with the second type systeminformation.

Example Embodiment 78

The wireless terminal of Example Embodiment 77, wherein the receiver isconfigured, in response to the request message and separately from theperiodic transmissions of the first type system information, to receivea transmission over the radio interface of the second type systeminformation.

Example Embodiment 79

The wireless terminal of Example Embodiment 77, wherein the value tag isvalid in a cell served by the access node.

Example Embodiment 80

The wireless terminal of Example Embodiment 77, wherein the value tag isvalid in a geographical area served by the access node and a group of atleast one other access node.

Example Embodiment 81

The wireless terminal of Example Embodiment 80, wherein the receiver isconfigured to receive a signal which defines the geographical area.

Example Embodiment 82

The wireless terminal of Example Embodiment 78, wherein the second typesystem information comprises plural parameters, the transmitter isconfigured to transmit the terminal-stored value tag in the requestmessage; the receiver is configured to receive the response message fromthe access node, the response message including changed ones of theplural parameters based on a comparison at the access node of thenode-reported value tag relative to the terminal-stored value tag; andthe processor circuitry is configured to use the changed ones of theplural parameters of the system information to replace correspondingparameters of the terminal-stored system information.

Example Embodiment 83

The wireless terminal of Example Embodiment 78, wherein the second typesystem information comprises plural parameters, the transmitter isconfigured to transmit an identification of a group of second typesystem information blocks in the request message; the receiver isconfigured to receive the response message from the access node, theresponse message including changed ones of the plural blocks of thegroup based on the comparison of the node-transmitted value tag relativeto the terminal-stored value tag; and the processor circuitry isconfigured to use the changed ones of the plural blocks of the group ofthe system information to replace corresponding blocks of theterminal-stored system information.

Example Embodiment 84

The wireless terminal of Example Embodiment 83, wherein at least one ofthe blocks of the group of the second type system information comprisesplural parameters, and the response message includes only changed onesof the plural parameters of the changed ones of the plural blocks of thegroup based on a comparison of the changed in the value tag relative tothe terminal-stored value tag; and the processor circuitry is configuredto use the changed ones of the plural parameters of the plural blocks ofthe group of the system information to replace corresponding parametersof corresponding blocks of the terminal-stored system information.

Example Embodiment 85

The wireless terminal of Example Embodiment 78, wherein the receiver isconfigured to receive in the response message an indication that therequested system information will be broadcast.

Example Embodiment 86

In another of its example aspects, the technology disclosed hereinconcerns a method in a wireless terminal that communicates over a radiointerface with an access node of a radio access network. In a basic modethe method comprises receiving from the access node a system informationavailability message comprising an identification of node-availablesystem information and a node-transmitted value tag associated with thenode-available system information; and, on the basis of thenode-transmitted value tag determining whether to request that thenode-available system information be transmitted to the wirelessterminal.

Example Embodiment 87

The method of Example Embodiment 86, wherein the method furthercomprises making a determination that terminal-stored system informationis current system information if a terminal-stored value tag associatedwith the terminal-stored system information is the same as thenode-transmitted value tag associated with the node-available systeminformation.

Example Embodiment 88

The method of Example Embodiment 87, wherein the method furthercomprises making a determination that the terminal-stored systeminformation is the current system information if the terminal-storedsystem information has been received within a predetermined time from acurrent time.

Example Embodiment 89

The method of Example Embodiment 87, wherein the method furthercomprises making a determination that the terminal-stored systeminformation is the current system information if the terminal-storedsystem information is received in a validity area of the access nodeupon which the wireless terminal is camping.

Example Embodiment 90

The method of Example Embodiment 86, wherein the method furthercomprises making a comparison of terminal-stored value tag and thenode-transmitted value tag; on the basis of the comparison to generate arequest message to request that the node-available system information betransmitted to the wireless terminal; and transmitting the requestmessage to the access node.

Example Embodiment 91

The method of Example Embodiment 90, wherein the method furthercomprises using the node-available system information to replace theterminal-stored system information.

Example Embodiment 92

The method of Example Embodiment 90, wherein the method furthercomprises receiving periodic transmissions of first type systeminformation over the radio interface; separately from the periodictransmissions of the first type system information, receiving secondtype system information over the radio interface; and wherein thenode-transmitted value tag is associated with the second type systeminformation.

Example Embodiment 93

The method of Example Embodiment 92, wherein the first type systeminformation comprises information which is periodically broadcasted bythe transmitter and which is required for initial access to the radioaccess network, and wherein the second type system information is notrequired for initial access to the radio access network.

Example Embodiment 94

The method of Example Embodiment 90, wherein the method furthercomprises receiving periodic transmissions of first type systeminformation over the radio interface, the period transmissions alsoincluding the node-available system information for second type systeminformation, the value tag being associated with the second type systeminformation.

Example Embodiment 95

The method of Example Embodiment 94, wherein the method furthercomprises receiving a transmission over the radio interface of thesecond type system information in a response message which is inresponse to the request message and separately from the periodictransmissions of the first type system information.

Example Embodiment 96

The method of Example Embodiment 94, wherein the value tag is valid in acell served by the access node.

Example Embodiment 97

The method of Example Embodiment 94, wherein the value tag is valid in ageographical area served by the access node and a group of at least oneother access node.

Example Embodiment 98

The method of Example Embodiment 97, wherein the method furthercomprises receiving a signal which defines the geographical area.

Example Embodiment 99

The method of Example Embodiment 95, wherein the second type systeminformation comprises plural parameters, and the method furthercomprises: transmitting the terminal-stored value tag in the requestmessage; receiving the response message from the access node, theresponse message including changed ones of the plural parameters basedon a comparison at the access node of the node-reported value tagrelative to the terminal-stored value tag; and using the changed ones ofthe plural parameters of the system information to replace correspondingparameters of the terminal-stored system information.

Example Embodiment 100

The method of Example Embodiment 95, wherein the second type systeminformation comprises plural parameters, and the method furthercomprises: transmitting an identification of a group of second typesystem information blocks in the request message; receiving the responsemessage from the access node, the response message including changedones of the plural blocks of the group based on the comparison of thenode-transmitted value tag relative to the terminal-stored value tag;and using the changed ones of the plural blocks of the group of thesystem information to replace corresponding blocks of theterminal-stored system information.

Example Embodiment 101

The method of Example Embodiment 100, wherein at least one of the blocksof the group of the second type system information comprises pluralparameters, and the response message includes only changed ones of theplural parameters of the changed ones of the plural blocks of the groupbased on a comparison of the changed in the value tag relative to theterminal-stored value tag; and the method further comprises using thechanged ones of the plural parameters of the plural blocks of the groupof the system information to replace corresponding parameters ofcorresponding blocks of the terminal-stored system information.

Example Embodiment 102

The method of Example Embodiment 95, wherein the method furthercomprises receiving in the response message an indication that therequested system information will be broadcast.

Although the processes and methods of the disclosed embodiments may bediscussed as being implemented as a software routine, some of the methodsteps that are disclosed therein may be performed in hardware as well asby a processor running software. As such, the embodiments may beimplemented in software as executed upon a computer system, in hardwareas an application specific integrated circuit or other types of hardwareimplementation, or a combination of software and hardware. The softwareroutines of the disclosed embodiments are capable of being executed onany computer operating systems, and is capable of being performed usingany central processing unit(s) (CPU(s)) architecture. The instructionsof such software are stored on non-transient computer readable media.

The functions of the various elements including functional blocks,including but not limited to those labeled or described as “computer,”“processor” or “controller,” may be provided through the use of hardwaresuch as circuit hardware and/or hardware capable of executing softwarein the form of coded instructions stored on computer readable mediums.Thus, such functions and illustrated functional blocks are to beunderstood as being either hardware-implemented and/orcomputer-implemented, and thus machine-implemented.

In terms of hardware implementation, the functional blocks may includeor encompass, without limitation, digital signal processor (DSP)hardware, reduced instruction set processor, hardware (e.g., digital oranalog) circuitry including but not limited to application specificintegrated circuit(s) [ASIC], and/or field programmable gate array(s)(FPGA(s)), and (where appropriate) state machines capable of performingsuch functions.

In terms of computer implementation, a computer is generally understoodto comprise one or more processors or one or more controllers, and theterms computer and processor and controller may be employedinterchangeably herein. When provided by a computer or processor orcontroller, the functions may be provided by a single dedicated computeror processor or controller, by a single shared computer or processor orcontroller, or by a plurality of individual computers or processors orcontrollers, some of which may be shared or distributed. Moreover, theuse of the term “processor” or “controller” shall also be construed torefer to other hardware capable of performing such functions and/orexecuting software, such as the example hardware recited above.

The functions of the various elements including functional blocks,including but not limited to those labeled or described as “computer,”“processor” or “controller,” may be provided through the use of hardwaresuch as circuit hardware and/or hardware capable of executing softwarein the form of coded instructions stored on computer readable mediums.Thus, such functions and illustrated functional blocks are to beunderstood as being either hardware-implemented and/orcomputer-implemented, and thus machine-implemented.

Nodes that communicate using the air interface also have suitable radiocommunications circuitry. Moreover, the technology can additionally beconsidered to be embodied entirely within any form of computer-readablememory, such as solid-state memory, magnetic disk, or optical diskcontaining an appropriate set of computer instructions that would causea processor to carry out the techniques described herein.

It will be appreciated that the technology disclosed herein is directedto solving radio communications-centric issues and is necessarily rootedin computer technology and overcomes problems specifically arising inradio communications. Moreover, in at least one of its aspects thetechnology disclosed herein improves the functioning of the basicfunction of a wireless terminal and/or node itself so that, for example,the wireless terminal and/or node can operate more effectively byprudent use of radio resources.

Although the description above contains many specificities, these shouldnot be construed as limiting the scope of the technology disclosedherein but as merely providing illustrations of some of the presentlypreferred embodiments of the technology disclosed herein. Thus, thescope of the technology disclosed herein should be determined by theappended claims and their legal equivalents. Therefore, it will beappreciated that the scope of the technology disclosed herein fullyencompasses other embodiments which may become obvious to those skilledin the art, and that the scope of the technology disclosed herein isaccordingly to be limited by nothing other than the appended claims, inwhich reference to an element in the singular is not intended to mean“one and only one” unless explicitly so stated, but rather “one ormore.” All structural, chemical, and functional equivalents to theelements of the above-described preferred embodiment that are known tothose of ordinary skill in the art are expressly incorporated herein byreference and are intended to be encompassed by the present claims.Moreover, it is not necessary for a device or method to address each andevery problem sought to be solved by the technology disclosed herein,for it to be encompassed by the present claims. Furthermore, no element,component, or method step in the present disclosure is intended to bededicated to the public regardless of whether the element, component, ormethod step is explicitly recited in the claims. No claim element hereinis to be construed under the provisions of 35 U.S.C. 112, sixthparagraph, unless the element is expressly recited using the phrase“means for.”

What is claimed is:
 1. A user equipment (UE) comprising: processingcircuitry configured to store a second type system information block,the second type system information block being associated with a firstvalue tag, the second type system information block being area specificor cell specific, an area specific second type system information blockbeing valid within an area, a cell specific second type systeminformation block being valid within a cell, and; receiving circuitryconfigured to receive, from a base station apparatus, a first typesystem information block comprising an indication and a second value tagassociated with the second type system information block, the indicationindicating whether the second type system information block is providedon-demand, wherein: the processing circuitry is configured to initiate areception procedure to obtain the second type system information block,based on whether the stored second type system information block is areaspecific or cell specific, the first value tag and the second value tag;the reception procedure comprises transmission of a request message forthe second type information block based on the indication; and the firsttype system information block is used for receiving minimum systeminformation, the minimum system information comprising, at least,information required for an initial access.
 2. The UE according to claim1, wherein for the stored second type system information blocks,validity is determined based on the first value tag and the second valuetag.
 3. The UE according to claim 2, wherein the second type systeminformation blocks comprises other system information not included inthe minimum system information.
 4. The UE according to claim 3, furthercomprising transmitting circuitry configured to transmit the requestmessage to the base station apparatus.
 5. A base station apparatuscomprising: processor circuitry configured to generate a value tagassociated with a second type system information block, the second typesystem information block being associated with a first value tag, thesecond type system information block being area specific or cellspecific, an area specific second type system information block beingvalid within an area, a cell specific second type system informationblock being valid within a cell; and transmitting circuitry configuredto transmit, to a user equipment (UE), a first type system informationblock and the second type system information block, the first typesystem information block comprising the value tag and an indication, theindication indicating whether the second type system information blockis provided on-demand, wherein; the value tag associated with the secondtype system information blocks and whether the second type systeminformation blocks is area specific or cell specific are used by the UEto initiate a reception procedure to obtain the second type systeminformation block; the reception procedure comprises transmission of arequest message for the second type information block based on theindication; and the first type system information block is used fortransmitting minimum system information, the minimum system informationcomprising, at least, information required for an initial access.
 6. Thebase station apparatus according to claim 5, wherein the second typesystem information block comprises other system information not includedin the minimum system information.
 7. The base station apparatusaccording to claim 6, further comprising receiving circuitry configuredto receive the request message from the UE.
 8. A communication method ofa user equipment (UE) comprising: storing a second type systeminformation block, the second type system information block beingassociated with a first value tag, the second type system informationblock being area specific or cell specific, an area specific second typesystem information block being valid within an area, a cell specificsecond type system information block being valid within a cell;receiving, from a base station apparatus, a first type systeminformation block comprising an indication and a second value tagassociated with the second type system information block, the indicationindicating whether the second type system information block is providedon-demand; and initiating a reception procedure to obtain the secondtype system information block, based on whether the stored second typesystem information block is area specific or cell specific, the firstvalue tag and the second value tag, wherein: the reception procedurecomprises transmission of a request message for the second typeinformation block based on the indication; and the first type systeminformation block is used for receiving minimum system information, theminimum system information comprising, at least, information requiredfor an initial access.
 9. The communication method according to claim 8,wherein for the stored second type system information block, validity isdetermined based on the first value tag and the second value tag. 10.The communication method according to claim 9, wherein the second typesystem information block comprises other system information not includedin the minimum system information.
 11. The communication methodaccording to claim 10, further comprising transmitting the requestmessage to the base station apparatus.
 12. A communication method of abase station apparatus comprising: generating a value tag associatedwith a second type system information block, the second type systeminformation block being area specific or cell specific, an area specificsecond type system information block being valid within an area, a cellspecific second tpe system information block being valid within a cell;and transmitting, to a user equipment (UE), a first type systeminformation block and the second type system information block, thefirst type system information block comprising the value tag and anindication, the indication indicating whether the second type systeminformation is provided on-demand, wherein: the value tag associatedwith the second type system information block and whether the secondtype system information block is area specific or cell specific are usedby the UE to initiate a reception procedure to obtain the second typesystem information block; the reception procedure comprises transmissionof a request message for the second type information block based on theindication; and the first type system information block is used fortransmitting minimum system information, the minimum system informationcomprising, at least, information required for an initial access. 13.The communication method according to claim 12, wherein the second typesystem information block comprises other system information not includedin the minimum system information.
 14. The communication methodaccording to claim 13, further comprising receiving the request messagefrom the UE.